Handle arithmetic exception for overlow

Instead of the try/catch, how about replacing ```rejectionPolicy.getCurrMaxTime().minus(windowMillis)``` with ```new DateTime(Math.max(windowMillis, rejectionPolicy.getCurrMaxTime().getMillis()) - windowMillis)```?

Or if you're not convinced that is cleaner, this looks cool as is so I am ok with merging it.