Many surround with templates unavailable

My last statement about dragging and dropping the try...finally is not correct.  I've looked into this more and can see the problem more clearly.

The 3 options that are avaiable to me when I press Ctrl+Alt+J are all marked Availalbe in C# 2.0+ files, while the missing options are marked Available in C#2.0+ files where statement is allowed.

Here is the code I selected when attemptin to use the surround template

        //if key already exists
        if(_keys.Count > insertAt && _keys[insertAt].Key.Equals(key))
        {
          _keys[insertAt] = new KeyValuePair<TKey, TValue>(key, value);
          Updated();
        }
        else
        {
          _keys.Insert(insertAt, new KeyValuePair<TKey, TValue>(key, value));
          Updated();
        }

I don't know if this worked in 4.1 or not, but it seems like it shold work.  I have no problem manually writing in the try/finally and compiling the code, here is the complete method with the try/finally typed in, this compiles successfullly.

    public void Put(TKey key, TValue value)
    {
      int insertAt = GetInserIndex(key);

      _lock.EnterWriteLock();

      try
      {
        //if key already exists
        if(_keys.Count > insertAt && _keys[insertAt].Key.Equals(key))
        {
          _keys[insertAt] = new KeyValuePair<TKey, TValue>(key, value);
          Updated();
        }
        else
        {
          _keys.Insert(insertAt, new KeyValuePair<TKey, TValue>(key, value));
          Updated();
        }
      }
      finally
      {
        _lock.ExitWriteLock();
      }

      CheckForInvalidChildren();
    }

Hello,

We appreciate your feedback. The corresponding JIRA request has been created,
and you are welcome to monitor its status at http://www.jetbrains.net/jira/browse/RSRP-102166.

You may want to check our request tracking policy here: http://www.jetbrains.net/confluence/display/ReSharper/ReSharperIssueTracker

Best regards,
- Development Team.

FYI, although marked as fixed for 1227, I just tried it using 1227 and the issue still exists.  I also commented on the jira issue.