IDE0220 on foreach (Match m in regex.Matches) – Should Not Occur

Using the following code snippet results in Roslyn analyzer adding an informational warning to the list of analysis results:

foreach (Match m in regex.Matches(text))
{
  ...
}

IDE0220  'foreach' statement implicitly converts 'object' into 'System.Text.RegularExpressions.Match'. Add an explicit cast to indicate your intention as it may fail at runtime.

MatchCollection.Item[], however, doesn’t return object. It returns a Match.

Version Used

.NET 6

Steps to Reproduce

1. Create a regular expression object.
2. Run the Regex.Matches() method on that regular expression and feed immediately to a Match variable in a foreach loop.

Expected Behavior

This should be analyzed by the Roslyn analyzer without flaw.

Actual Behavior

The Roslyn analyzer adds an information to the analysis result (roughly translated by me from German to English):

IDE0220  'foreach' statement implicitly converts 'object' into 'System.Text.RegularExpressions.Match'. Add an explicit cast to indicate your intention as it may fail at runtime.

[m-gallesio]

This still applies to .NET 7.0.

[twest820]

That looks like #60120 rather than #60210. MatchCollection defines

    public IEnumerator GetEnumerator() => new Enumerator(this);

    IEnumerator<Match> IEnumerable<Match>.GetEnumerator() => new Enumerator(this);

with Enumerator having

        public Match Current { get { ... } }

        object IEnumerator.Current => Current;

Naively, I’d expect both foreach and the rule to find the strongly typed path but perhaps that’s not what happens.