Creating an inner-class prompts a complete test detection process

The slowest thing with Infinitest is the finding of the tests. So it is a little frustrating to sometimes see Infinitest do a detection of the tests from scratch.
The most obvious case is when we create or delete inner-classes, as we frequently do when using Guava's functional-like features (such as Functions).

For example, writing this causes Infinitest to look for all the tests again:

public class MyTest {
    @Test
    public void shouldWork() {
        assertTrue(new Object() {
        } instanceof Object);
    }
}

Deleting the anonymous class causes Infinitest to look for all the tests again:

public class MyTest {
    @Test
    public void shouldWork() {
        assertTrue(true);
    }
}

Performance improvements on that aspect would be nice.

Thanks.