Hi, thanks for posting and for the feedback.

NCrunch is somewhat limited in its code coverage analysis by the fact that it only analyses line-by-line, whereas more specialised code coverage tools (such as the one in Visual Studio) will analyse any statement or code component with debugging information available.

The line-by-line decision was made in an effort to provide better performance while processing large amounts of code coverage, and to try to maintain simplicity through the UI.

There have been many good suggestions about how NCrunch might able to provide better visual representation of partial-line coverage (for example, perhaps by having a half-coloured marker). Although these suggestions certainly have merit and I can appreciate the value of making the coverage more accurate, at the moment this area isn't really a design goal and the structural limitations of NCrunch's processing would make it very difficult to implement without greatly decreasing the performance of the engine.

Of course, things always change. There is always the possibility to pursue this later in future.