Superior Drummer's MIDI drum loops don't map properly with my user-created drum map in X3

Update:  
I solved my own problem with a work-around. Here's how I did it in case someone would search and find this helpful: 
I use Superior Drummer 2.4.2 inside of Sonar X3e. My problem as already stated was that I had created a custom drum map in Sonar X3 that involved remapping the location of the drum sounds inside of Superior Drummer via SD's "learn" function. I did this so that I could place the drum sounds on very specific keys on my MIDI keyboard just the way I like them for easy/ergonomic playability. (The default SD NY drum map in Sonar and the default mapping in SD have the sounds sparsely placed all over the place on my MIDI keyboard and on the drum map on the screen, which I found very disorganized and some of the sounds weren't mapped on my keyboard at all). So the remapping in SD and custom drum map I made in Sonar worked just fine -- until I wanted to audition and drag and drop some of the MIDI drum loops that comes with SD. Toontrack had mapped the sounds in those loops to their own specific locations that were not sympathetic to my user-created drum map and so while auditioning the loops I would typically only hear kick drum and maybe hi hat and the rest of the sounds were unmapped/unheard or the wrong sound got triggered, like a tom instead of snare etc.  
The work-around was to use two instances of Superior Drummer; one for my user-created drum map and the other strictly for auditioning the loops - and in each instance I have a different mapping scheme; the SD instance just for auditioning has the "General MIDI" (or whatever its called) mapping preset selected so that the Toontrack MIDI loops can be auditioned and triggered correctly - and the second instance of SD has my customized mapping preset selected that works with my user-created drum map in Sonar X3e. After I audition a loop and drag/drop it to the MIDI track that corresponds with that specific instance of SD and I see/hear where the notes should be mapped, I then manually drag that MIDI data from the "audition track" to the MIDI track that has my user-created drum map on it. Then, I have to manually move some of the notes that ultimately end up "unmapped" to their correct locations in the Piano Roll/Drum Map view in Sonar. And while that's somewhat a PITA to have to do, at least I am able to first audition the loops to see/hear where the individual drum notes should be triggered before I manually move the loop to the other track with my user-created drum map on it where I then have to manually move some of the unmapped/wrongly mapped drum notes to the correct notes. I think this is the only way to be able to have both a user-created drum map for assigning notes to specific keys on a MIDI keyboard AND be able to audition loops from Toontrack's MIDI packs and have them trigger correctly. If there is, in fact, another/better way then please let me know. Hope this helps someone.

Hey Mike. Thanks for pointing that out, as I wasn't using SD's browser but Sonar's. I now see that SD's browser is way better and you pointing that out has actually helped me in another area, so thanks. There's still the issue with the default mapping in SD and it's loops vs my user-created map, though. My custom drum map has moved things around for the sake of mapping the sounds to specific keys on a MIDI keyboard - and the mapping for SD's loops are not sympathetic to that, i.e. they don't "smartly" follow my mapping scheme and so when using my custom drum map to audition the loops, be it via Sonar's or SD's browser, some of the sounds get triggered incorrectly (tom instead of snare, e.g.) or don't trigger at all. When auditioning the loops in SD's browser I still have to flip back and forth between SD's default mapping preset so the loops trigger correctly, then adjust back to my custom preset when I'm ready to drag the loop over - and once that's done I still have to manually move some of the drum notes to the correct location in PRV to get them to trigger the right sound when using my custom drum map. The only way I can see getting around that is if SD had some kind of "smart" function that somehow followed my custom remapping. Does that makes sense, or am I still going way out of my way to do something simple (wouldn't be the first time)? Thank man