Answers

I was able to repro the bug no matter what PST the selected item is in, but the bug has been reported so that's about all we can do until the product group decides whether to fix it or not. About the only other thing that can
be done is if you were to open a support incident, as it's a bug any charges would ultimately be refunded, and see if a hot fix can be arranged.

I don't have a Windows 8 VM set up yet, I tested this on Outlook 2013 x86 release version running on Windows 7 x86 with a POP3 account. I can't repro the problem there.

I took your sample code and put it in the VBA project, I ran a search in Sent Items and repeated a different search in Inbox. In both cases I selected an item from the search return in the UI and then ran the code. The EntryID
was printed to the Immediate window with no errors.

Can you repro on a different OS than Windows 8? Can you repro this on another machine?
You're testing with the release version and not a beta version?

Did you have more than 1 PST file opened, and were you set up with your profile to use a POP3 account? I was able to repro the bug running on Win7x86 with Outlook 2013 x86 with scope set to All Outlook Items or All Mailboxes
with 4 PST files opened.

I was able to repro the bug no matter what PST the selected item is in, but the bug has been reported so that's about all we can do until the product group decides whether to fix it or not. About the only other thing that can
be done is if you were to open a support incident, as it's a bug any charges would ultimately be refunded, and see if a hot fix can be arranged.

There is no fix yet as far as I can tell, based on the latest available code.

If this is important you should open a support case with MS support and try to get a fix. The bug has been reported to the product group, but from there it's up to them to triage bugs and decide which to fix and when.