This is indeed a good way to guide your debugging. Using coverage information can sometimes reduce the search space.

Nice little article. It's a good way to point out that aiming for the lowest Big-O approach is often not what you want in terms of performance. Always keep the context in mind, and in doubt measure.