How to be sure a JS redirect occurs before triggering web analytics code?

Question

I've got a client who is setting up a system where a certain segment of visitors to a page "A" will receive a Javascript redirect to another page "B". (I know, not ideal but not my idea...)

They're using a Javascript tag-based web analytics solution (Omniture SiteCatalyst) which is deployed on both pages.

My question is, for visitors who we redirect, can we ensure that the redirect will fire and that they'll be "off" of page "A" before the page "A" web analytics code fires and triggers a page view?

Is there something that needs to be done programatically, and is there a more or less "foolproof" way to make sure that page "A"'s analytics code won't fire, or will any solution have some leakage depending on variations in browsers and net / client PC speed and so forth?