Source: #100

Should be MUCH faster than this. Can likely use lookup tables to trade memory for CPU time?

#411 improved this, to some extent:

Further improvements will require simplifying the comparator function, especially the numerous calls into the Waypoints API. I don't know what the hell is going on there, but it sure isn't fast:

Ignore the significant overhead introduced by adding profiling labels; the gist is that it's mostly the API calls that slow this down tremendously.