Comment 4 for bug 867302

Yes, this is still pending. There are a number of things hampering this:

1. (design) where to store the timers -- each timer needs to subsume timers for the modules and UDFs invoked from the current query recursively. Easiest would be global timers accessed via System::properties, but that incurs the synchronization cost and will still not work with multi-threading

1. zorbacmd is supposed to limit itself to the public API. Thus, the above timers need to be visible via the API, or we need to break the rules yet again.