I wholeheartedly agree with Brad on this. It's a tool that provides a smell that should be further investigated. The code coverage "score" is arbitrary, but using it to baseline what is normal and good should help flag missing tests should the figure decrease. 

Also, SQL Cover is free and open source, so there's absolutely no harm in using it, particularly if already using a automated build / CI tool.