When debugging a Module, it's possible to use Step Into to execute assignments one by one (instead of executiong the entire Assignment Statement at once). This is a great feature, but it could use some improvements:

1. There's no visual clue this happens. The "cursor" (arrow) stays on the Assignment Statement node, until the last of the assignments has been executed. It would be great if the Assignment would open in the Property Pane (where it normally opens when clicked), with the cursor/arrow pointing at the currently executed line.
2. The Step Into steps into everything, including User Functions. If the first assignment uses a User Function, that Function is stepped into directly, which can be confusing. So if 1 above is implemented, SS should first show the cursor at the first assignment, before executing anything. Also, it should then be possible to use Step Over / Step Into / Step Out having a scope for that Assignment Statement (so Step Over executes the current assignment, Step Into steps into the first User Function, Step Out executes all assignments and returns the cursor to the next Statement to execute).
3. If 2 is implemented, also make sure to select (or otherwise mark) the User Function, if any, so it's clear what the user is going to Step Into. If there are multiple User Functions, they should be marked one after the other.

EDIT: The above should also go for Structure/List mappings.