If you tell Profiler not to filter out its own queries, you'd probably see it calling these stored procedures:

* <a href="http://msdn.microsoft.com/en-us/library/ms190362(v=sql.90).aspx">`sp_trace_create`</a> to create a trace
* <a href="http://msdn.microsoft.com/en-US/library/ms186265(v=sql.90).aspx">`sp_trace_setevent`</a> to add or remove events and columns (can only be called on a stopped trace)
* <a href="http://msdn.microsoft.com/en-US/library/ms174404(v=sql.90).aspx">`sp_trace_setfilter`</a> to apply a filter to a trace (can only be called on a stopped trace)
* <a href="http://msdn.microsoft.com/en-us/library/ms176034(v=sql.90).aspx">`sp_trace_setstatus`</a> to start and stop a trace

As described by <a href="http://msdn.microsoft.com/en-us/library/ms191443(v=sql.90).aspx">the documentation, you execute the procedures in this order:

1. Create a trace by using `sp_trace_create`.
2. Add events with `sp_trace_setevent`.
3. (Optional) Set a filter with `sp_trace_setfilter`.
4. Start the trace with `sp_trace_setstatus`.
5. Stop the trace with `sp_trace_setstatus`.
6. Close the trace with `sp_trace_setstatus`. 

You will end up with a `.trc` file that you can then open in SQL Profiler.