Clover-for-Eclipse may load intermediate coverage results and not load subsequent coverage updates

If a test run takes longer than the refresh period for coverage, intermediate coverage data may be loaded (depending on flush settings) and the final coverage data is not subsequently loaded.

The quick solution is to hold off loading coverage while ever a coverage.db.liverec file is present.

The longer term solution will be a combination of:

• track the last modified stamps and file sizes for coverage recording file
• implement an undo framework for all recording files so that intermediate coverage loads can be undone and updated coverage can be appended