I claim this and show some work already done.

ConstructorShouldNotCallVirtualMethodsRule

This rule warns the developer if any virtual methods are called in the 
constructor of
non-sealed type. The problem is exact method that will be executed is not known
before runtime. Also such virtual calls may be executed before the constructor 
of
deriving type is called, thus making possible mistakes.

Bad example:
class A {
    public A ()
    {
        this.DoSomething ();
    }
    protected virtual void DoSomething () { }
}

class B : A {
    private int x;

    public B ()
    {
        x = 10;
    }

    protected override void DoSomething ()
    {
        Console.WriteLine (x);
    }
}

B b = new B (); // outputs zero because B constructor hasn't been called yet

No good examples here, I think (any example avoiding this is good).

You got it (but I won't have time to review anything before tonight)

GetEntryAssemblyMayReturnNullRule

Calling Assembly.GetEntryAssembly () not from the main application domain will 
always
result in null, and this may become a problem for ASP .NET applications.

Bad example:

// ASP .NET page
Response.WriteLine (Assembly.GetEntryAssembly ().CodeBase); // null reference 
exception

It all looks good. BTW nice tests on GetEntryAssemblyMayReturnNullTest to get 
both
case working :)

I'll only be able to test them tonight but, as I don't anticipate any issue, 
you can
go ahead with another task.

But before that please supply good examples for both, it's not hard and will 
make my
life easier when I update the web site documentation ;-)

Good example for ConstructorShouldNotCallVirtualMethodsRule:

class A {
    public A ()
    {
    }

    public void Run ()
    {
        // here we can call virtual methods
        this.DoSomething ();
    }   

    protected virtual void DoSomething () { }
}

class B : A {
    private int x;

    public B ()
    {
        x = 10;
    }

    protected override void DoSomething ()
    {
        Console.WriteLine (x);
    }
}

B b = new B ();
b.Run (); // outputs 10 as intended


Good example for GetEntryAssemblyMayReturnNullRule:

// executable
public class MainClass {
    static void Main ()
    {
        Console.WriteLine (Assembly.GetEntryAssembly ().CodeBase);
    }
}

aha! you were too quick and forgot to check for HasBody ;-)
I made the 2 liners fixes and committed to SVN.

Good work :)
Sebastien