One more important thing to note:
I was able to successfully recreate this issue on a virtual Win7 x64 PC on VMware. Looks like the issue is not local to the user's PC, profile, or copy of Outlook 2013. I'm wondering if this is a bug in Outlook 2013. Has anyone else noticed this issue in the...