1st of all...ClrMamePro corrects several nodumps to correct checksums to prevent overwriting with dummyfiles when fullmerging. 2nd of all...nodump biossets aren't counted. 3rd of all..there are some other operations to fix bad datfile/mameoutput settings.

One of the main reasons are: MAME outputs several roms more than once. This is based on the procedure -listinfo works. So a baddump of one set can be listed like 4 times because the driver loads the roms that way. ClrMamePro imports it only once of course.

Turn on show datfile bugs and set it to show all...and reget the data (not from the cache). You'll see what I mean ;) You will dozens of errors ;)

You can show all nodump and all baddump (and inverted crc32s) when enabling some scanner (advanced) options. Simply compare them with your results ;)=
Esp. for baddumps you also have to count possible inverted crc32s since they were used before the baddump flag.