Pin-point the exact cause and nature of bottlenecks using the Performance profiler. This profiler lets you not only time the execution of routines and lines, but also track other crucial aspects of the application's performance: check whether the performance bottlenecks are caused by system-level functions, or by an excessive number of memory page faults; determine how well the CPU can predict the execution flow of your code, and so on. Using the Performance profiler you can not only find a performance bottleneck, but also find out what caused that bottleneck.

Find un-tested sections of source code at both routine and source code line levels. AQtime offers developers integrated code Coverage analysis. This invaluable tool allows you to discover which functions and/or lines of code have not been tested as you run through a test cycle. With this feature you will no longer have to ask questions like "Did we really test and debug our applications thoroughly?"

Trace the calling routes for application functions with the Function Trace profiler. Using this profiler, you can easily find how a routine can be called and know the actual call stack for each call route. The profiler also times individual function calls and logs function parameters used for the call. The profiler results give you valuable information about the application's execution and lets you detect whether the application functions as expected. All without requiring you to insert special tracing messages into your application's source code!

Track and hunt down memory allocation and usage issues that are critical to the overall health and maintenance of your applications. AQtime's Allocation profiler tracks the creation and deletion of application objects as well as allocations and de-allocations of memory blocks. This profiler lets you easily see what objects exist in memory when results are generated. By comparing two result sets generated by the profiler, you can easily determine which objects were created or deleted between two result generations.
You can use the Allocation profiler along with AQtime's Monitor panel - a tool that gathers and displays information on memory and resource usage in real time.

Check whether your application releases all of its allocated resources using AQtime's Resource profiler. Using this profiler you can quickly discover what bitmaps, icons, BSTR strings and other resources are allocated by your application. By comparing two results you can easily find which resources were allocated or released between two result generations.

Visualize the caller-callee relationships of the application routines. Using the Call Graph and Call Tree panels you can easily see which routines call what routines in your application.

Explore the binary code of your application's routine using the Disassembler panel.

Check possible links between classes and routines. Using the Static Analysis profiler you can explore the debug information of your application and determine what routines include calls to other routines and what class methods call methods of other classes. The Static Analysis will also tell how many loop or conditional assembler instructions a routine's binary code contains, what is the routine size in bytes and in source code lines, whether the routine uses MMX, SSE or SSE2 instructions.
A powerful addition to the Static Analysis profiler is the PE Reader panel. It also performs the analysis of your application statically and provides detailed information about modules used by the application. For example, it shows tables of imported and exported routines, module base addresses, entry points of routines and their offsets in the import address table, plus much more.

The Sequence Diagram Link profiler, like Static Analysis, explores the debug information of your application, tracks links between routines (what calls what) and builds a UML-style diagram of functions calls in Microsoft Word or Microsoft Visio. This profiler is an excellent tool to know the links between routines without running an application.

Track exceptions that occur during the application execution using the Exception Trace Profiler.

Trace how your applications uses dynamic link libraries using the Load Library Tracer profiler.

Monitor the usage of API calls to produce code that works as expected across all Windows platforms via AQtime's Platform Compliance Profiler.