One of my favorite tools for SQL Server 2000 is Read80Trace. It reads a trace file and summarizes the SQL to identify the statements and stored procedures that use the most resources. It appears Microsoft won't be releasing a version that will read SQL Server 2005 trace files.
That gave me a good reason to write my own version that will read SQL Server 2000 and 2005 trace files. It has a commnand-line version and a GUI version. The GUI version will import the trace files and let you query them based on application, host and login and sort based on CPU, Reads, Writes, Duration and number of executions. The data is stored in a database so you can query it yourself or store it for future use.
The GUI application can send feedback directly to me. I'd like to hear what you think and any suggestions on how to improve it. It does require SQL Server 2005 on the computer where it runs since it uses SMO to query the trace file.