I am investigating mechanisms to improve C code quality

I am a strong believer in using tools, however to be effective, such
tools need to be simple and effective. For dynamic analysis, such tools
do exists, however for static analysis I expect there might be better
tools
available than lint. The most promising candidate I have come up with so
far, is a product named QAC. Does anyone here have experience QAC or
is there better products available?

Furthermore, I want to enforce an official coding standard, i.e. a
sub-set of the C language. I am aware of MISRA-C, but is there better
sub-sets to consider? Or has MISRA-C become de facto standard
for usage of C in safety related development?

What is the best tool to enforce MISRA-C?

(I have read a report on an analysis of 6 MISRA-C tools, apparently
both correctness and number of false positives was a big problem,
e.g. not all tools looked mature and practical for real projects).

That said, the two best newsgroups I can think of for discussing these
issues are comp.programming (marginal) and comp.software-eng.

<off topic>
MISRA C is an excellent set of guidelines, I agree with almost all of
them.  But the best analysis tool in the world is peer review, some
kind of informal code review or formal code inspection.
</off topic>