Avoid call_user_func_array in query method

>If we take this route, we should remove any trace of overloading and request that end users use executeQuery when they want to use that method and query when they want to use the other method.

I'd be all for this, but it would be a breaking change and require core code refactoring. Wasn't sure if that was feasible at this point.