Abstract members are not correctly filtered out of available options for further processors

[Philip Peitsch]

Abstract members appear to trip up NGineer, appearing as available when they will not actually be writable. Demonstration hierarchy is as follows:

public class ParentClass
{
    public abstract string Property { get; }
}

public class ChildClass : ParentClass
{
   public string Property { get { return "Hello"; } }
}

Update: this seems to be triggered directly by the IgnoreAll() method