Hi,
> There are also Test Complete objects like aqFile, aqDateTime, aqString etc
> which provide alot of the functionality JavaScript support libraries offer anyway
> so their usefulness for me diminished.
The only note is that you are binding yourself to the given language when you start using some third-party library. If you are working for a single project / employer this might be quite acceptable.
But if you reuse test code for different projects that use language other than JScript, you have no chance but to re-create everything from a scratch. Whereas, in case of using built-in objects, you are getting portable code that requires just a syntax corrections, that are done, usually, pretty easy.
Because of this, my preference is to use native TestComplete programming objects as much as possible, even if / when they have exactly matching equivalents in the current project language.