Microsoft Windows Vista RTM support.

Support for Microsoft .NET Framework 3. AQtime can now profile .NET Framework 3 applications and work on computers that have .NET Framework 3 installed.

Support for the Intel Core processors family.

A new Class Name column has been added to the Call Stack pane of the Details panel that displays the Allocation profiler results. This column displays the name of the object class that contains the routine that allocated memory blocks.

Interfaces that provide access to the AQtime engine via COM have been improved. Now the IntegrationManager object contains a new ClearResults method and a new ResultReady property.

Sometimes, AQtime could crash when closing.

In certain cases, AQtime could not read debug information for .NET assemblies.

Sometimes, AQtime hung the process to which it tried to attach.

The Coverage profiler did not trace calls to unmanaged routines from managed code.

AQtime did not read information about classes of Visual C++ 6 MFC applications from the application's debug info.

The Allocation profiler did not show leaks caused by the modules added to the Setup panel even if the Show leaks for Setup modules option was enabled.

If the Show leaks for Setup modules option was enabled, AQtime could crash upon updating the Call Graph panel with information on the managed object selected in the Allocation profiler results.

The Allocation profiler counted the number of instances (objects) that existed in memory incorrectly.

In certain cases, the Allocation profiler reported a memory overwrite error, though the memory was not overwritten.

If the Check memory bounds option was enabled, an access violation could occur when closing the application that was profiled with the Allocation profiler.

The Resource profiler reported that the CoInitialize function caused a memory leak.

When filtering events in the Event View panel, only the parent event of the type that did not match the filter was hidden, but its child events were still displayed. Now AQtime hides the child events as well.

In certain cases, errors occurred when working with data and charts in the Monitor panel.

Sometimes, profiling a service in the Service Profiling Mode caused the "Operation aborted" error under Windows XP Professional x64 Edition.

Under the x64 platform, AQtime could not start profiling an ASP.NET application in ASP.NET mode, and displayed an error message.

The message displayed upon trying to attach a 64-bit module to a 32-bit process was incorrect.

AQtime integrated into Microsoft Visual Studio 2005 could not start profiling a just created application.

After obtaining a project from the source control system, or checking the project in, if the user chose not to clear the file's Read-Only attribute, AQtime closed the project without any notification.

AQtime options did not include the Show at startup option for the Assistant panel. It was possible only to change this option directly from this panel.

The Context-sensitive option of the Assistant panel worked only during the first profiler run of each AQtime session.

An error occurred upon deactivating the Assistant and Setup plug-ins from AQtime integrated into Microsoft Visual Studio 2005.

AQtime could crash upon reactivating the Native Code Support plug-in.

The Clear Results menu and toolbar item was hidden.

AQtime displayed a number of error messages when the user was trying to add a great number of procedures to a class-level area.

The message that appears upon adding a project to a source control system contained certain helper symbols. AQtime project files (.aqt) had old-style icons.