Comment 6 for bug 284125

So updating the TestResult protocol to report on TestResource activity is interesting. There is however one key aspect that is problematic: run()/__call__() doesn't pass the TestResult object through to the test, setup, and teardown methods. In particular, we'd want it in setup and teardown.

Some thoughts:
 - we could look up the stack to find the result object.
   a bit gross, but only twice per test object.
 - we could just not report when OptimisingTestSuite isn't being used
   counterintuitive.

Opinions solicited.