Isolated attribute, Isolate.CleanUp, and MockManager.ClearAl

Hi,

I have something similar to the following in a test:

    [TestFixture]
    [Isolated]
    public class SomeTests 
    {

        [SetUp]
        public void SetUp()
        { 
            Isolate.CleanUp();
            try
            {
                Isolate.Fake.StaticConstructor(typeof (Config));
            }
            catch (TypeMockException e)
            {
               //ignore - the static constructor has probably already been faked 
            }
            Isolate.Fake.StaticMethods(typeof(Config));
            ...some more fakes...
        }

When I remove the line that says 'Isolate.CleanUp' and I run the test along with other tests that also try to fake out the 'Config' class, the test fails.

However, the documentation clearly states that the 'Isolated' attribute and 'Isolate.CleanUp' can be used interchangeably (https://www.typemock.com/Docs/UserGuide/newGuide/html/M_TypeMock_ArrangeActAssert_Isolate_CleanUp.htm). This doesn't work for us; is this a bug, is the documentation incorrect, or are we doing something wrong?

Also, we use both AAA and the classic API in our tests (because we started using the classic API and haven't rewritten all our tests to use AAA.) Some instances of the 'Config' class will have been mocked using MockManager.Mock<Config>(). Does that mean I also need to call MockManager.ClearAll() as part of my setup method?

I think my main question is: what do I need to do to make sure that the mocks are cleared before each test is run? Should I use the 'Isolated' attribute, Isolate.CleanUp, MockManager.ClearAll, MockManager.Init, or a combination of the above?

Thanks,
Nick