This test was meaningless
This test misrepresented Jobs' claims, and thus produced irrelevant results.
Jobs said that Flash was responsible for the vast majority of web browser crashes, not Mac OS crashes. This is not just possible, but likely.
Jobs said that Flash was a CPU/resource hog. He said Flash, not just Flash playing h.264 video. It is obvious, but irrelevant, that playing h.264 video efficiently comes down to CODEC performance, which requires hardware acceleration to be CPU efficient. But to support Flash, you have to not only support h.264 video (which is very rarely used in Flash), but the full range of Flash scripted interaction, and of course all of the older CODECs. And that is what consumes CPU and RAM that makes Flash suck battery/CPU/RAM. To disprove this you would need to run a wide range of interactive Flash apps, and try to prove that none of them are slow or bloated. Or you could try to prove that Flash Lite is not only efficient but runs all Flash on the internet. Good luck with that.
Jobs' actual claim was that to support the full range of Flash on the web, the iPad would have to have the CPU and RAM of a desktop computer, at which point it would cost much more and have a much shorter battery life, and would on top of that be less stable (because Flash is unstable). So his interactive media strategy is to support h.264 video, and JavaScript/HTML5, which are well defined and can be optimized to run efficiently and reliably.