Mocking a function to return an actual COM Object fails

I didn't have any issue reproducing this in a fairly simple testcase:

using System;
using Microsoft.Office.Interop.Excel;
using Microsoft.VisualStudio.TestTools.UnitTesting;
using TypeMock.ArrangeActAssert;

namespace TypeMock8._1CannotReturnCOMObject
{
    [TestClass]
    [Isolated]
    public class UnitTest1
    {
        public interface IRangeGetter
        {
            Range GetRange();
        }
        [TestMethod]
        public void TestMethod1()
        {
            RunExcelTest(
                (range, getter) =>
                {
                    // Error here -> TypeMockException: *** Can not fake methods defined in mscorlib, try faking the defining type
                    Isolate.WhenCalled(() => getter.GetRange()).WillReturn(range);

                    Range actual = getter.GetRange();

                    Assert.AreEqual(range, actual);
                });
        }

        [TestMethod]
        public void TestMethod2()
        {
            RunExcelTest(
                (range, getter) =>
                {
                    Isolate.WhenCalled(() => getter.GetRange()).DoInstead(ctx => range);

                    // Error here -> TypeMockException: *** Cannot return System.__ComObject value from method that returns Microsoft.Office.Interop.Excel.Range
                    Range actual = getter.GetRange();

                    Assert.AreEqual(range, actual);
                });
        }

        private static void RunExcelTest(Action<Range, IRangeGetter> testToRun)
        {
            Application excel = new ApplicationClass();
            try
            {
                Workbook wb = excel.Workbooks.Add();
                Worksheet ws = (Worksheet)wb.Worksheets.Add();
                Range range = ws.Range["A1"];
                IRangeGetter getter = Isolate.Fake.Instance<IRangeGetter>();

                testToRun(range, getter);
            }
            finally
            {
                // Shut down Excel
                foreach (Workbook workbook in excel.Workbooks)
                {
                    workbook.Close(SaveChanges: false);
                }
                excel.Quit();
            }
        }
    }
}

I'm using Excel from Office 2010.  My test project included a reference to Microsoft.Office.Interop.Excel and was built targeting framework 4.0 with the CPU target set to x86.  I don't know if those last two matter, but that matches our product's build environment.