ObjAsm & code analysis

Remembering some disassembly made Druck’s !ARMAnalyser tool and a few issues in my own code, I was wondering if some code analysis could not be included in the analyser to caution against:
- use of non-initialised register (would require some kind of macro to list register used as parameters for functions).
- use of conditional after a BL/SWI
- use of conditional related to flags that could not possibly have been modified by the flag modifying instructions that precede.
- performance issues.