So what are you trying to capture? Is it individual statements from a stored procedure? You're using the sp_statement_completed event. The "sp" at the start stands for stored procedure. If you're trying to capture individual statements from a batch, you want sql_statement_completed. These are both very granular events. Generally, I use sql_batch_completed and rpc_completed as the two events I use to watch T-SQL batch operations and stored procedures (or prepared statements). They capture overall behavior of the batch or procedure, not the individual statement. None of these need to add the global field you added. They will all, by default, capture the appropriate calling command. They should show you what you're looking for, including execution time (in microseconds, not milliseconds, worth noting), I/O, CPU and quite a bit more.
You're not doing anything wrong and I sure don't think I've rebuked you in some way, so don't worry, let's just talk about what you're trying to get done.
If you want to see a bunch of examples, I'd suggest going to my blog.