Right, I've captured the Resident Evil 5 Shanty Town level up to the chainsaw guy, and included a 'spin the camera around the main character' moment at the beginning of the video.
The results are:
28,886 frames captured, 29.97fps, 0.37% torn frames.
For the public arena level, I captured it at 1080p60, then edited out all the black screens that crop up before and after cut-scenes as these world skew the frame analysis. I also did the 'spin around the character' exercise at the beginning of the stage too.
17,032 frames captured, 29.2fps, 5.73% torn frames.
This is clearly at odds with what Quaz is seeing. My feeling is that if there is a bug in the Capcom engine, it only affects certain 360s. My unit is an NTSC Elite (Zephyr model). The only other explanation is that the 1080p signal is not running at the right timing for the display. Quite why only Capcom games are affected is a mysterious though.
The only other thing I should point out is that I'm running at 1920x1080, ie the console sees TrueHD as a DVI monitor rather than an HDMI display. What I have noticed is that if you select 1920x1080, it asks you to confirm that the picture is OK before locking the resolution. If you say NO, it invokes a second 1920x1080 mode using slightly different timings.
However I also use an HDCP decrypter that identifies itself as an HDTV, and this brings up the more usual HDTV settings on the console set-up. In previous tests, this has produced the same output as 1920x1080.
In terms of these Resi captures though, I can scan through and confirm the results by eye, and I can see the torn frames - where they are - too.