Put another way: if we re-jigger the handling of the unmapped reads so that they're evenly distributed across the genomic partitions, in what way is this (functionally) different from using the existing RangePartitioner class?