I suspect this is why 12157692622039623539 wasn't included:

12157692622039623539 === 12157692622039624000 // -> true

Javascript numbers just don't go that high, you'd need to use strings instead (which still wouldn't satisfy this kata because it tests for numbers).

Yeah, but if the author were to add an if statement which started calculating only if the top of the range was very high, they could keep the advantage of speed whilst making their solution general purpose.

I think it is up to you. The link is for better explanation.