> @phoyd I don't think it was brought to Microsoft's attention (the odds of it ever being addressed are next to none, since this would be a VBA problem / not an Excel type library problem; Excel's type library is actively maintained and regularly extended, but not VBA itself), from what I recall this weird behavior was accidentally discovered and immediately treated as an oddity that Rubberduck could/should be inspecting for.
Since 32-bit works fine it appears to be a x64-only bug related to a