Trevor Williams - 2009-08-05

I believe that a good solution to this problem is to run Covered in a hybrid mode where only memory coverage within FOR loops is simulated by Covered. This coverage information would then be pulled out of the inlined code.