thanks much for your reply. Unfortunately, I don't think there's much one could do - short of adding functionality to allow recording of form submission and input in a Silverlight site - that would fix this problem.
It's not so much a problem with WPM as a limitation. If you look at my other post regarding challenges with measuring transactions in Silverlight, you can see that I'm getting inaccurate time readings as well.
I've been tasked with trying to automate, monitor, and measure performance of web transactions for this particular Silverlight site, and it's very, very difficult to do - I'm not sure how much that has to do with WPM, though.
It's more about the site itself. I've hit the wall on how to best do this.