"COVERAGE IS TO TESTING AS COMPILING IS TO CODING."

That's a nice way of thinking about coverage.

" you only get one chance to test that section of code correctly, since after the first test which covers the code, you no longer have the obvious warning of uncovered code"

In case you haven't seen it in action, Clover's per-test coverage can help with this, by letting you view all tests that cover a specific line of code, or enter a specific class. You can also view the coverage of a specific file, provided only by a single, or set of tests.

An example of this is:
http://clover.atlassian.com/browse/guice/

This makes it possible to see if a line is covered directly by a test that has an assertion, or whether it is only covered in passing.

Cheers,
Nick Pellow