Design question/intent before merging

In GeometryWrapper.java, in the case of having only 1 field we have a direct range comparison method. The old version of this did not use a fuzzy compare (i.e. double + epsilon range).

The new version does

• Is this what we want? I would argue yes - if we use it anywhere, we should use it everywhere (deterministic behaviour). Also, since this is a "rejection" type operation (i.e. we aren't generating a list, rather we are culling an already existing list) we don't have an danger of "wrong" data.
• This required changing one of the tests to make pass (always a chancy thing) - the value a particular field was incremented by (1E-13) previously caused a failure when the match was exact, but now passed (since the tolerance was 1E-12. The value was reduced to 1E-10 to cause it to fail again. Hopefully I caught the intent of the test.