Corrected the way -bf-mem-footprint reports results

While the code associated with maintaining the memory footprint seems
okay, the code associated with outputting the memory-footprint data
was egregiously wrong with respect to being used without
-bf-unique-bytes, with respect to detecting the 100% case, and with
respect to usage with bf_categorize_counters().