Hi -

Thanks for sharing this. Right now NCrunch's code coverage resolution works to the line only (not to the statement), so as you've described, there is granularity that is lost here in the coverage reporting.

This has been an often requested feature although at this stage I haven't yet found a way to implement it. The complexity of the NCrunch algorithm that maps code coverage is staggeringly complex, and getting it to perform acceptably with statement level coverage is a fairly epic challenge.

I appreciate you mentioning this though, as it does help to underscore the need.


Cheers,

Remco