Try and make it clearer to the end user what is happening during test optimization.

When Clover is run in debug mode, it would be ideal if a user could infer from the logs exactly why each test is either being run, or not being run.

Specifically some feedback from customers:

For instance I'd like to see which classes clover recognizes as changed ?
I'd like to know if clover thinks that a file has changed (but maybe just can't match the corresponding test-file) or if the problems start, because clover isn't even detecting a change ?