Taking a second look at this a bit further, I actually do see this being a current issue in the latest release of SmarterStats 9.x. I will go ahead and get this added to list of issues to address in the next minor release of SmarterStats.
Thanks for taking the time to report this.