And what, in iOS 5 was a clear, obvious, intuitive way to (1) see what tracks are stored locally on the device, and which tracks aren't, (2) to remove tracks from local storage, and (3) to download individual tracks for local storage has been rewritten in iOS 6 in a way in which all three of these things are still technically possible, sure, but are anything but intuitive or elegant.
I'm sorry, but any instruction that begins with "first, disable iTunes Match" is a step back in UI design from iOS 5.
If Apple was concerned about some users not understanding the paradigm of locally stored vs streamed music and hence not understanding why their storage capacity was depleting over time, they could still have modified iOS to stream/cache (instead of auto-download) non-local tracks as they are played, AND left in the "cloud download" button (so that there is a visual indication to users who want it as to what tracks are not local) AND left in the ability to swipe/delete a locally-stored track.
Each track could have three possible states:
(1) Non-local
(2) Local (cached)
(3) Local (downloaded)
In state 1 and 2, the "cloud download button" would be shown. If pressed, the track would be downloaded and now be state 3. If the track was simply played (without pressing the "cloud download button") then it would become cached (or remain cached).
In state 3, the "cloud download button" would not be shown. A swipe/delete on this track would remove it from the device, and it would now be state 1.
The current behavior of iOS 5 would be preserved, with the ostensible concerns being addressed in iOS 6 covered as well.
I actually completely agree with you and would prefer that it was designed in just that way. My goal in this thread has not been to debate how Match could have been made better in iOS 6, but to counter the claims that music can no longer be deleted from the device piecemeal.
The system does work if we follow the instructions. Whether we think the process is well designed or not is a topic for another thread.
I have stated many times that it is my opinion that Apple chose this method because of the possibility of confusion, I have never said that I agreed with or liked that method. In the meantime, I just need to understand how the current system works so I can make it work for my needs.
I still don't see what this has to do with data usage though.