SA1513 fires in switch statements

SA1513 fires erroneously for switch statements with enforced braces. A block of code structured in the following manner

int i = 0;
switch (i)
{
    case 1:
    {
        // Thing
        break;
    }
    case 2:
    {
        // Other thing
        break;
    }
    default:
    {
        break;
    }
}

will raise two instances of the inspection at lines 8 and 13, respectively. I would assume that this is not intended behaviour, and that no instances should be raised. If this is intended, it would be a good candidate for addition into the json configuration, as it is a common pattern for switch statements and introducing blank lines between the cases would go against this.

[Ruhrpottpatriot]

I want to second this proposal. The rule also fires (I guess by design) when you put the break outside the block braces. At least in my eyes the following looks very weird:

case statement: 
{
    // Some code
}

break;
case anotherStatement:
    // More Code

From intuition I’d expect this form:

case statement: 
{
    // Some code
}
break;

case anotherStatement:
    // More Code

[maxkoshevoi]

Is an external implementation that fixes this ready somewhere?