RichDet - Improved interpolator range checking

During the development of !643 (merged) I noticed a rare corner case where the range checking failed and an out-of-bounds array access would occur. This MR addresses the issue. The issue is not hit during normal processing (I only saw it with some specific tests I added temporarily) so should not result in any observable diffs.