Optimize and clarify closest-point computation in BoundaryCheck
It feels like compilers should be smarter sometimes... but a ~3x speedup on failing boundary checks with tolerances is nothing to snide at.
It feels like compilers should be smarter sometimes... but a ~3x speedup on failing boundary checks with tolerances is nothing to snide at.