Test coverage is a very dangerous metric. IMO it will only be useful the day that we find a way to not take into account those tests that are testing implementation details. Every time that I see a high number being enforced, the end result is always a disaster: lots of poor quality tests that are only there in order to bump up that metric. Those tests are poison: they don't aim to test correctness, they make refactors/improvements a PITA, they just lock you down to a concrete implementation and they don't even give you any guarantees that your code works correctly.
And what happens when you tell the story and everybody just completely ignores you?
TBH I find that a lot more frustrating than ppl missing the point on what you were trying to say. That is exactly is what happened to me a week ago... I will keep on trying, though :-)