len for 0..0 returns 1

[m4b]

I can't see a semantics where this would ever be valid. Is there a reason for this behavior? (+1 is explicitly added to max in len method)

[m4b]

I actually think I understand this now; is the range 10..10 representing the memory at point 10?

I think then your upper bound is inclusive.

Is this invariant propagated and enforced throughout the crate as well as in theban_interval_tree ?

At very least (assuming this interpretation is true), should definitely document this explicitly, as it is very surprising...