Slight hitch in the analogy - insurance payments cost something. Running DBCC checks costs nothing. What did this clown think he was saving by avoiding DBCC checks? A couple seconds of his own time to glance at the results? A few milliwatts of processor power? Wear and tear on his drives from some disk reads?

Claiming that "we've never had a problem" is pretty lame reasoning when part of the job is the ensure that problems don't crop up. I'm with you, Steve - I'd likely fire someone who displayed such a cavalier attitude towards system safety. Shitcanning a lax DBA is a sound problem-prevention technique on the part of a careful and conscientious manager, just like running DBCC is problem-prevention technique on the part of a good DBA.